upload image

Suggestion 161 Invalid yDNA Haplogroup

Privacy Level: Open (White)
Date: 19 Jul 2022
Location: Worldwidemap
Surnames/tags: data_doctors db_error_161
Profile manager: Aleš Trtnik private message [send private message]
This page has been accessed 522 times.

Description of Error - 161: Invalid yDNA Haplogroup

The yDNA Haplogroup should be entered using the Y-Chromosome Consortium’s (YCC) recommended short form name. For example R-M323.


Content of info column: The Haplogroup.

Possible Causes

  • Use of the old Haplogroup names
  • Typo in the Haplogroup names

Action Steps

  • Find the new format of "R1b1a2a1a1b4" haplogroup. You can use a search engine (e.g. DuckDuckGo, Google) to find the new name
  • Correct the Haplogroup typo.

Error Status

For each Error you can set status. You can set it as Corrected, Not corrected, False Error, Proposed merge or just add a Comment.

If there are related errors for the profile, you will also see them on status page.

Full description is available on Status Help Page.

Questions and Discussions on this Error

You can read what other people have asked here db_error_161.

You can also share your best practices, experiences, problems about the Error by posting a question in G2G. If you create a new G2G discussion for this Error, add tag data_doctors and db_error_161.

Technical Stuff

All profiles with the yDNA test entered are checked against the familytreedna haplogroup list, yBrowse haplogroup list and SNP index.

Suggestion reports

You can see the weekly prepared list of the latest suggestions prepared on May 12th 2024. You can also get the online report on WikiTree+.
This page is part of the Data Doctors Project.
 
Latest report: May 12th 2024.
Data Doctors Challenge: Add_Existing_Connections_XIX and .
Custom reports by: Suggestion lists, Unsourced lists, Unconnected lists.
See for custom reports and statistics and our Video Collection.
 
Latest ProjectBox Report: Project Report
Latest Categories Report: Categories Suggestions Report







Collaboration
  • Login to edit this profile and add images.
  • Private Messages: Send a private message to the Profile Manager. (Best when privacy is an issue.)
  • Public Comments: Login to post. (Best for messages specifically directed to those editing this profile. Limit 20 per day.)


Comments: 9

Leave a message for others who see this profile.
There are no comments yet.
Login to post a comment.
This explanation is poorly written and confusing.

It should say: The yDNA Haplogroup should be entered using the Y-Chromosome Consortium’s (YCC) recommended short form name. For example R-M323. (Note, an R-M32 branch does not exist.)

posted by Jim Toth
Thanks. I updated the help page.
posted by Aleš Trtnik
I have 2 error 161's in my profiles. First is Mead-2618. His haplo group from FTDNA is I-P37. The other is Baker-21968. His Haplo group from FTDNA is I-M253. The only I's you have on your list are IMS.
posted by Barbara (Baker) Mead
I'm receiving suggestion 161, Invalid yDNA Haplogroup, for "R-L1066.1" on my own profile, Mills-7869.

R-L1066.1 is correct according to 23andMe: https://you.23andme.com/reports/paternal_haplogroup/ "Your paternal line stems from a branch of R-M343 called R-M269 [...] Your paternal haplogroup, R-L1066.1, traces back to a man who lived less than 10,000 years ago."

R-L1066.1 is recognised by ISOGG and FTDNA: https://www.genetichomeland.com/dna-marker/chromosome-Y/L1066.1

I think the regex needs to be expanded beyond three digits.

I think you are correct. I will study the groups a bit more and try to correct the expression.

Maybe it would be best to get the full index of Haplogroups instead of regex.

posted by Aleš Trtnik
I now imported the list of yDNA Haplogroups and I am comparing entries to it.

https://docs.google.com/spreadsheets/d/1UY26FvLE3UmEmYFiXgOy0uezJi_wOut-V5TD0a_6-bE/edit#gid=1934392066

Suggestions should be updated in an hour or two.

posted by Aleš Trtnik
I don't know where that Google doc comes from, but it is missing my haplogroup, so I am still getting the error. I am R-FGC66323 and have been for some time. See https://www.genetichomeland.com/dna-marker/chromosome-Y/FGC66323 for the parents and children of my clade. I suppose I could move it up one level to L1029, but that's a much larger clade (931 members) versus mine (182 members). I don't see why I need to change my scientifically determined (by Family Tree DNA) haplogroup to satisfy somebody's arbitrary list of clades. Both Genetic Homeland (above) and Scaled Innovation have no problem pulling a different list which includes my haplogroup. Maybe you should ask one of them what source they use? See http://scaledinnovation.com/gg/snpTracker.html?SNP=FGC66323 for my haplogroup at Scaled Innovation.
posted by Bill Schultz
I think with the latest update to the suggestion calculation (see G2G), your haplogroup should be ok.
posted by Aleš Trtnik
Basically what is needed is to make sure the first letter is consistent across multiple testers. For practical purposes we can ignore everything else on the haplogroup.
posted by Ed Street

Categories: DD Suggestions Help